wayland: don't handle buffer release centrally
authorRay Strode <rstrode@redhat.com>
Tue, 2 Feb 2016 19:36:25 +0000 (14:36 -0500)
committerRay Strode <rstrode@redhat.com>
Sat, 6 Feb 2016 13:02:57 +0000 (08:02 -0500)
commit40e91195ad8a20c073789dad192e7aaaf9af6eca
treee1668280359210620abb956b2939ffd008da1e2f
parent2c300081c4fc4db6a345041cbf4942cb99cea793
wayland: don't handle buffer release centrally

Right now we handle buffer releases coming from the
compositor in a central place. We add a listener when
first creating the shared buffers.

This is problematic because a buffer can only have
one listener on it at once so users of the buffer
can't get notified when it's released.

This commit moves the buffer listener code from the
centrally managed display code to the cursor and window
code.

https://bugzilla.gnome.org/show_bug.cgi?id=761312
gdk/wayland/gdkcursor-wayland.c
gdk/wayland/gdkdisplay-wayland.c
gdk/wayland/gdkwindow-wayland.c